Not sure what's happening on npm publishing (canary):

npm error code E404
npm error 404 Not Found - PUT https://registry.npmjs.org/mysql2 - Not found
npm error 404
npm error 404  'mysql2@3.12.1-canary.51da6534' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.

• https://github.com/sidorares/node-mysql2/actions/runs/13143979519/job/36679467571

However, the idea is to wait and see what's missing in #2289 before merging this release or add the documentation about disableEval without adding Cloudflare Workers to its context.

@sidorares, could you check if the NPM_TOKEN has expired? I tried other packages and everything worked fine. Also, the link https://registry.npmjs.org/mysql2 is valid, so the 404 seems to be an authentication failure.

@wellwelwel yes it is expired, updating now

sorry, I had a long break from github, just catching up

re cloudflare workers support: definitely worth merging 'no eval' feature, however network wrapper code might be no longer relevant - https://x.com/CloudflareDev/status/1884699456018301020

@wellwelwel NPM_TOKEN updated

sorry, I had a long break from github, just catching up

Thanks and no worries 🙋🏻‍♂️

re cloudflare workers support: definitely worth merging 'no eval' feature, however network wrapper code might be no longer relevant - https://x.com/CloudflareDev/status/1884699456018301020

It's great, I believe that with this, the only remaining piece is to document it properly (as done in #2289).

🤖 Release is at https://github.com/sidorares/node-mysql2/releases/tag/v3.13.0 🌻